Added FAQ Section Including Common Question/Answer Regarding Timestamp Discrepancies #6980
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alanjcharles
approved these changes
Aug 26, 2024
silesky
approved these changes
Aug 27, 2024
stayseesong
requested changes
Aug 27, 2024
|
|
||
| ## FAQ | ||
|
|
||
| ### Why Are Events Received with Timestamps Set in the Past or Future? |
There was a problem hiding this comment.
Suggested change
| ### Why Are Events Received with Timestamps Set in the Past or Future? | |
| ### Why are events received with timestamps set in the past or future? |
Comment on lines
+309
to
+322
| 1. **Overriding Timestamp Value:** | ||
| - When a manual timestamp is set in the payload with a date in the past, it can cause events to appear as if they were sent earlier than they actually were. | ||
|
|
||
| 2. **Analytics.js Source with Retries Enabled:** | ||
| - The [Retries](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#retries) feature supports offline traffic by queuing events in Analytics.js. These events are sent or retried later when an internet connection is available, keeping the original timestamp intact. | ||
|
|
||
| 3. **Mobile App Backgrounded or Closed:** | ||
| - If a user closes the app, events may be queued within the app. These queued events won't be sent until the app is re-opened, potentially in the future, leading to timestamp discrepancies. | ||
|
|
||
| 4. **Inaccurate Browser/Device Clock Settings:** | ||
| - Timestamps can be incorrect if the client's device time is inaccurate, as the `originalTimestamp` relies on the client device's clock, which can be manually adjusted. | ||
|
|
||
| 5. **Traffic from Internet Bots:** | ||
| - [Internet Bots](https://segment.com/docs/guides/ignore-bots/#whats-a-bot) can sometimes send requests with unusual timestamps, either intentionally or due to incorrect settings, leading to discrepancies. |
There was a problem hiding this comment.
Suggested change
| 1. **Overriding Timestamp Value:** | |
| - When a manual timestamp is set in the payload with a date in the past, it can cause events to appear as if they were sent earlier than they actually were. | |
| 2. **Analytics.js Source with Retries Enabled:** | |
| - The [Retries](https://segment.com/docs/connections/sources/catalog/libraries/website/javascript/#retries) feature supports offline traffic by queuing events in Analytics.js. These events are sent or retried later when an internet connection is available, keeping the original timestamp intact. | |
| 3. **Mobile App Backgrounded or Closed:** | |
| - If a user closes the app, events may be queued within the app. These queued events won't be sent until the app is re-opened, potentially in the future, leading to timestamp discrepancies. | |
| 4. **Inaccurate Browser/Device Clock Settings:** | |
| - Timestamps can be incorrect if the client's device time is inaccurate, as the `originalTimestamp` relies on the client device's clock, which can be manually adjusted. | |
| 5. **Traffic from Internet Bots:** | |
| - [Internet Bots](https://segment.com/docs/guides/ignore-bots/#whats-a-bot) can sometimes send requests with unusual timestamps, either intentionally or due to incorrect settings, leading to discrepancies. | |
| * **Overriding Timestamp Value:** When a manual timestamp is set in the payload with a date in the past, it can cause events to appear as if they were sent earlier than they actually were. | |
| * **Analytics.js Source with Retries Enabled:** The [Retries](/docs/connections/sources/catalog/libraries/website/javascript/#retries) feature supports offline traffic by queuing events in Analytics.js. These events are sent or retried later when an internet connection is available, keeping the original timestamp intact. | |
| * **Mobile App Backgrounded or Closed:** If a user closes the app, events may be queued within the app. These queued events won't send until the app is re-opened, potentially in the future, leading to timestamp discrepancies. | |
| * **Inaccurate Browser/Device Clock Settings:** Timestamps can be incorrect if the client's device time is inaccurate, as the `originalTimestamp` relies on the client device's clock, which can be manually adjusted. | |
| * **Traffic from Internet Bots:** [Internet Bots](/docs/guides/ignore-bots/#whats-a-bot) can sometimes send requests with unusual timestamps, either intentionally or due to incorrect settings, leading to discrepancies. |
stayseesong
approved these changes
Aug 27, 2024
|
Thank you for your contribution! Your pull request is merged, but may take a day or two to appear on the site. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed changes
Merge timing
ASAP once approved
Related issues (optional)
Slack: https://twilio.slack.com/archives/CALA7QMJQ/p1724679975057569